🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/20737

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 54 New Failures, 133 Cancelled Jobs, 8 Unclassified Failures

As of commit 472be1c with merge base f41d66d ():

This comment was automatically generated by Dr. CI and updates every 15 minutes.

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@claude [ci-fix-attempt 1/3]

The trunk CI workflow has failed on this automated PyTorch pin bump PR.
Failed run: https://github.com/pytorch/executorch/actions/runs/28785286440

Please:

1. Read the Dr. CI comment on this PR for a summary of which jobs failed and whether they are flaky. Ignore failures marked as FLAKY.
2. Use your CI tools to download the failure logs for the non-flaky failing jobs
3. Identify the root cause of the failure
4. If this is a build or test failure caused by PyTorch API changes, fix the ExecuTorch code to be compatible with the new PyTorch version
5. If this is a c10 header sync issue, the headers have already been synced by the pin bump script — the issue is likely in ExecuTorch code that uses those headers
6. Run lintrunner -a on any files you change
7. Push your fix as a new commit to this PR branch

Important constraints:

• Do NOT modify torch_pin.py or .ci/docker/ci_commit_pins/pytorch.txt — the pin itself is correct
• Do NOT modify files under runtime/core/portable_type/c10/ unless the sync introduced a new API that ExecuTorch code needs to adapt to
• Focus on fixing ExecuTorch code to be compatible with the new PyTorch APIs
• If this is a major BC-breaking change that requires architectural discussion, say so clearly and stop — do not attempt a fix

Claude finished @pytorchupdatebot's task in 6m 12s —— View job

CI Fix — PyTorch pin bump [attempt 1/3]

• Read Dr. CI summary and identify non-flaky failures
• Download failure logs for representative failing job
• Identify root cause
• Determine whether this is fixable in ExecuTorch code

Root cause

All the non-flaky failures share one cause. The test-binary-size and vit failures are downstream docker exec ... failed wrappers around the same underlying export crash, and the test-qnn-python-imports job was cancelled (retry, not a real failure). The real error is:

File ".../torchao/quantization/pt2e/quantizer/port_metadata_pass.py", line 181,
      in _port_metadata_for_input_quant_nodes
    torch.ops.aten.transpose.Dimname,
  File ".../torch/_ops.py", line 1243, in __getattr__
    raise AttributeError(...)
AttributeError: The underlying op of 'aten.transpose' has no overload name 'Dimname'

PyTorch nightly dev20260705 removed the Dimname overload of aten.transpose. torchao's port_metadata_pass.py references torch.ops.aten.transpose.Dimname in a hardcoded op list, so it now raises at import/pass-construction time. This breaks every XNNPACK quantization-delegation export (mv2, mv3, vit, ic3, ic4, resnet18/50, emformer, add_mul, …), which is exactly the set of failing jobs.

Why I am not pushing a fix

The failing code is not in ExecuTorch — a repo-wide search for transpose.Dimname returns nothing here; the traceback is entirely inside the installed torchao package. ExecuTorch installs torchao from the third-party/ao submodule (install_requirements.py:74), and the pin-bump script updated only torch_pin.py, pytorch.txt, and the c10 headers — it did not bump third-party/ao, so torchao is stale relative to the new nightly.

This is a cross-repo BC break that ExecuTorch source cannot patch. The fix belongs upstream in pytorch/ao (drop/guard the removed transpose.Dimname overload), followed by bumping the third-party/ao submodule here to a torchao commit compatible with dev20260705. Per the "major BC-breaking change → say so and stop" constraint, I'm stopping rather than attempting an out-of-scope fix.

Recommended next steps

• Land/locate the torchao fix that removes the reference to the now-deleted aten.transpose.Dimname overload in torchao/quantization/pt2e/quantizer/port_metadata_pass.py.
• Bump the third-party/ao submodule pin in this PR (or a companion PR) to that torchao commit.
• Re-run CI.

cc @jakeszwe — this pin bump needs a coordinated third-party/ao submodule bump; it is not fixable in ExecuTorch code alone.
· branch automated/pytorch-pin-bump-dev20260705

Superseded by newer pin bump.